Rendered version https://kedro--4443.org.readthedocs.build/en/4443/data/kedro_dvc_versioning.html

Sorry for being a pain in the neck 🙏🏼

I think we need to decide who's the audience of this guide.

* Is it users that don't know much about Kedro or DVC?

* Or is it Kedro users that already know their way around more or less?

In the first case, I think this should almost read like a tutorial and the commands and the steps should be fool-proof. For example, instead of clarifying about the .gitignore after dvc add, we should add a step before that reads like

Since the spaceflights-pandas starter ignores everything under data/ by default, you have to update the .gitignore file as follows:

Otherwise, if we assume that the reader knows a bit about Kedro, we can make the guide less prescriptive. In that case, then the sentence from the beginning "For this example, we will be using a Kedro spaceflights-pandas starter project" should be modified, maybe like

For example, you can use the spaceflights-pandas starter, see the documentation about starters [link]

As an example of this, I've been always inspired by the work @/melissawm did on the NumPy tutorials, for example

* https://numpy.org/numpy-tutorials/content/tutorial-svd.html

* https://numpy.org/numpy-tutorials/content/tutorial-ma.html

We don't have to follow the same structure but at least having a clear reader persona in mind helps structure the rest of the document 💡

These are some fair points. I think the step-by-step tutorial approach might be better, I usually don't like to make assumptions about an user's knowledge level.

RTD failure is unrelated

/home/docs/checkouts/readthedocs.org/user_builds/kedro/checkouts/4443/docs/source/notebooks_and_ipython/notebook-example/add_kedro_to_a_notebook.md:155:broken link: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311 (404 Client Error: Not Found for url: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311)

(they took down our blog post? 🥹)

RTD failure is unrelated

/home/docs/checkouts/readthedocs.org/user_builds/kedro/checkouts/4443/docs/source/notebooks_and_ipython/notebook-example/add_kedro_to_a_notebook.md:155:broken link: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311 (404 Client Error: Not Found for url: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311)

(they took down our blog post? 🥹)

It moved to medium

I resolved all review comments from previous passes that no longer apply, please have a look at the rest.

RTD failure is unrelated

/home/docs/checkouts/readthedocs.org/user_builds/kedro/checkouts/4443/docs/source/notebooks_and_ipython/notebook-example/add_kedro_to_a_notebook.md:155:broken link: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311 (404 Client Error: Not Found for url: https://towardsdatascience.com/five-software-engineering-principles-for-collaborative-data-science-ab26667a311)

(they took down our blog post? 🥹)

It moved to medium

What is the new link? The main branch is still using the broken one.

New link https://medium.com/towards-data-science/five-software-engineering-principles-for-collaborative-data-science-ab26667a311